Common Errors Encountered When Publishing an Asset
Missing fields
This error occurs when a user tries to publish assets with incorrect and incomplete fields.
Message: "Required field."
How can this be resolved? Fill in all required fields and try publishing again.
Could not connect to endpoint
When publishing a new data asset, the error occurs upon input of the data asset’s endpoint under the 'Connect Your Asset' step. This happens because an invalid URL is connected to the data endpoint or the data endpoint belongs to an asset in a private datastore and is blocked by a firewall.
Message: "Error: Could not connect to endpoint."
How can this be resolved?
- Ensure the URL of the data asset is valid, check for any typo errors in the URL.
- Make sure your private datastore allows connections from Acentrik or is set to public.
- Alternatively, you can also request to set up a private edge computing node infrastructure dedicated to your enterprise
Edge node list appears empty
This error occurs when the edge node was not set up by instance/group or the chain ID was not configured.
How can this be resolved? Set up the edge node properly or configure the chain ID.
Docker image
This error occurs when the user inputs an invalid Docker image or if the Docker image is not supported.
Message: "Please make sure your public Docker image is entered correctly."
How can this be resolved? Ensure the Docker image is valid and supported.
No compatible algorithm
This error occurs when selecting a trusted algorithm for publishing an asset, but none are showing.
For more information, visit No Compatible Algorithm.
Retry transaction
This error usually happens during the asset publishing process after confirming to publish an asset. This error commonly occurs in the stepper of publishing an asset when one of the transactions is not complete.
Message: "Sorry, something went wrong. Please try again."
How can this be resolved?
- Click Retry to try again.
- If you would like to exit the transaction, click 'Cancel'.